Skip to content

Onboarding SCS Hardware Landscape#341

Merged
fkr merged 5 commits intomainfrom
feat/onboarding-scs-hardware-landscape
Feb 6, 2026
Merged

Onboarding SCS Hardware Landscape#341
fkr merged 5 commits intomainfrom
feat/onboarding-scs-hardware-landscape

Conversation

@depressiveRobot
Copy link
Contributor

@depressiveRobot depressiveRobot commented Dec 19, 2025 •
edited
Loading

This PR adds instructions on how to get access to the SCS Hardware Landscape.

Closes #322

@depressiveRobot depressiveRobot self-assigned this Dec 19, 2025
@depressiveRobot depressiveRobot added the documentation Improvements or additions to documentation label Dec 19, 2025
berendt
berendt requested changes Dec 19, 2025
View reviewed changes
@depressiveRobot depressiveRobot requested review from berendt, jklare and michaelbayr and removed request for berendt and matofeder January 29, 2026 13:29
@depressiveRobot
Copy link
Contributor Author

depressiveRobot commented Jan 29, 2026

As suggested by @fkr, the Project Board should take responsibility for the access to the HW Lab in the future. Hence the request for review by the Project Board here :)

fkr
fkr approved these changes Feb 1, 2026
View reviewed changes
Copy link
Member

@fkr fkr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@fkr
Copy link
Member

fkr commented Feb 1, 2026

Imho we should also document, what the PB needs to do with those PRs (since the access mgmt setup is then handled by B1, who currently do the OPS for the HW Lab.)

@fkr fkr force-pushed the feat/onboarding-scs-hardware-landscape branch from dde01e9 to 7e02fdb Compare February 1, 2026 08:47
@fkr fkr requested a review from berendt February 1, 2026 08:47
@depressiveRobot
Copy link
Contributor Author

depressiveRobot commented Feb 3, 2026

Imho we should also document, what the PB needs to do with those PRs (since the access mgmt setup is then handled by B1, who currently do the OPS for the HW Lab.)

Good point. However, someone from the Project Board should document it in this PR. I don't want to tell the Board what to do 😅

@fkr
add that the mail should include the intended usage.
a042a32 
While here, write one sentence on what the PB does with the mail.

Signed-off-by: Felix Kronlage-Dammers <[email protected]>
@fkr
Copy link
Member

fkr commented Feb 4, 2026

Imho we should also document, what the PB needs to do with those PRs (since the access mgmt setup is then handled by B1, who currently do the OPS for the HW Lab.)

Good point. However, someone from the Project Board should document it in this PR. I don't want to tell the Board what to do 😅

I've added couple sentences with a042a32.
This should address this as well as what @garloff raised on Monday's PB: we'd like a short summary of the intended use.

garloff
garloff approved these changes Feb 4, 2026
View reviewed changes
@fkr @garloff
Update community/cloud-resources/cloud-resources.md
cf32d34 
Co-authored-by: Kurt Garloff <[email protected]>
Signed-off-by: Felix Kronlage-Dammers <[email protected]>
@fkr fkr merged commit 687ea19 into main Feb 6, 2026
8 checks passed
@fkr fkr deleted the feat/onboarding-scs-hardware-landscape branch February 6, 2026 07:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@garloff garloff garloff approved these changes

@fkr fkr fkr approved these changes

@jschoone jschoone Awaiting requested review from jschoone

@michaelbayr michaelbayr Awaiting requested review from michaelbayr

@jklare jklare Awaiting requested review from jklare

@berendt berendt Awaiting requested review from berendt

Assignees

@depressiveRobot depressiveRobot

Labels

documentation Improvements or additions to documentation

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Extend Cloud-Ressources Docs in regards to SCS HW Lab

4 participants

@depressiveRobot @fkr @berendt @garloff